Method for updating connection profile in content delivery service

ABSTRACT

A method for updating a connection profile in a content delivery service by a dynamic content delivery (DCD) terminal, comprises: receiving, from a server, a connection profile update message including a connection profile; transmitting, to the server, a connection profile update confirmation message in response to the reception; transmitting, to the server, a session deactivation request message based on the connection profile; and transmitting, to another server, a session activation request message base on the connection profile.

RELATED APPLICATION

The present disclosure relates to subject matter contained in aprovisional application No. 61/043,046, filed on Apr. 7, 2008, aprovisional application No. 61/049,776, filed on May 2, 2008, and apriority Korean Application No. 10-2008-0084969, filed on Aug. 29, 2008,which are herein expressly incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a method for updating configurationinformation such as a connection profile.

2. Background of the Invention

In general, content delivery service is performed based on configurationinformation, for example, a network interface.

The content delivery service includes various types of services, and adynamic content delivery (DCD) service has been recently proposed.

The DCD service is performed to deliver content to a terminalperiodically or according to a user's request.

The DCD service includes a pull method for delivering content to aterminal according to a user's request, a push method for unilaterallydelivering content to a terminal, a broadcast method for broadcastingcontent to a plurality of terminals, etc.

Referring to FIG. 1, the DCD service includes a DCD terminal 100, acontent provider (or content providing server) 200, and a DCD server 300(or Service Provider SP) for receiving the content from the contentprovider 200 and providing it to the DCD terminal 100 according to auser's configuration.

The DCD terminal 100 includes a DCD client 101, and a DCD enabled clientapplication 102.

The DCD client 101 receives the content from the DCD server 300 throughan interface therebetween.

The interface between the DCD client 101 and the DCD server 300 includesDCD-1 interface, DCD 2-interface, and DCD-3 interface.

The DCD-1 interface supports a service based on the PULL method, theDCD-2 interface supports a service based on the PUSH method, and theDCD-3 interface serves to transmit and receive a control signal, etc.

The DCD enabled client application 102 performs various functions byusing content received from the DCD server 300, and includes variousapplications such as a browser and an RSS viewer.

The DCD enabled client application 102 includes an application profilecorresponding to configuration information for the DCD service.

Hereinafter, the operation among the components of FIG. 1 will beexplained.

The DCD enabled client application 102 of the DCD terminal 100 informsitself to the DCD client 101, and registers to the DCD client 101 so asto receive content from the DCD server 300. For the registration, theDCD enabled client application 102 delivers an application registrationrequest message to the DCD client 101. Here, the applicationregistration request message may include the application profile. And,the application registration request message may further includeinformation such as a user's preference and personalization. This allowsthe DCD server 300 to deliver a channel guide about a user's interestchannel (e.g., today weather) to the DCD terminal 100 based on theuser's preference and personalization information.

The DCD client 101 registers to the DCD server 300. Here, the DCD client101 delivers the application registration request message to the DCDserver 300. The application registration request message may include theapplication profile. As aforementioned, the application registrationrequest message may further include information such as a user'spreference and personalization.

The content provider 200 generates a channel formed as a plurality ofsimilar contents are grouped. The content provider 200 registers channelmetadata, information about a plurality of channels that can be providedby itself, to the DCD server 300. Then, the content provider 200provides the channel metadata to the DCD server 300.

The DCD server 300 makes a channel guide through the channel metadata bythe plurality of content providers 200, and provides the channel guideto the DCD terminal 100.

The DCD enabled client application 102 of the DCD terminal 100 providesthe channel guide to a user, thereby allowing the user to subscribe tointerest channels. Once the user wants to subscribe to his or herinterest channels, the DCD enabled client application 102 delivers thesubscription request to the DCD server 300 through the DCD client 101.Then, the DCD server 300 delivers the subscription request to thecontent provider 200.

The content provider 200 delivers the channel metadata to the DCD server300, and the DCD server 300 delivers the metadata to the DCD enabledclient application 102 through the DCD client 101. Here, the contentprovider 200 may further deliver content metadata about content insidethe channels to the DCD server 300.

The channel metadata is stored at a lower hierarchy of the applicationprofile of the corresponding DCD enabled client application 102 thatplays back content of the subscribed interest channel.

FIG. 2 shows details about the application profile and channel profile,and a relation therebetween.

Referring to FIG. 2, the channel metadata is located at a lowerhierarchy of the application profile. And, the content metadata islocated at a lower hierarchy of the channel metadata.

The application profile includes an application-id parameter indicatingan ID of a corresponding application, an application-descriptionparameter indicating information of an application (e.g., applicationname), a channel-discovery-notification parameter indicating whether tonotify a new channel or not, a DCD-3-connection-profile-name parameterindicating a name of configuration information about the DCD-3 interfacesuch as a connection profile, and a DCD-3-connection-profile parameterincluding the configuration information about the DCD-3 interface suchas the connection profile. As aforementioned, the connection profile islocated at a lower hierarchy of the application profile. Accordingly,when the DCD enabled client application 102 registers to the DCD client101 so as to inform itself and to receive content from the DCD server300, the connection profile is delivered to the DCD client 101 from theDCD enabled client application 102 with being included in theapplication profile. Once receiving the connection profile, the DCDclient 101 checks validity of the connection profile, activates aconnection with the DCD server 300, and sets a session with the DCDserver 300.

The DCD-3-connection-profile parameter includes the connection profile.Here, the connection profile includes an address of the DCD server,information about a proxy server, etc. The DCD client 101 performs aconnection with the DCD server 300 through the DCD-3 interface by usingthe connection profile inside the application profile.

The content metadata includes a connection profile about the DCD-1interface, and a connection profile about the DCD-2 interface.

The connection profile about the DCD-1 interface is included in theapplication profile. The application profile is generated when amanufacturer presents out a terminal installed with the application, orwhen the manufacturer installs a new application. This may cause changeof the connection profile to be impossible, and thus service can not beperformed when the DCD server designated in the connection profile ismal-operated. Furthermore, when a plurality of DCD terminals have thesame connection profile, they are connected to the same DCD server. Thismay cause an overload.

When receiving the channel metadata by subscribing to the channel, theconnection profile about the DCD-2 is received together with the channelmetadata. The connection profile can be received only when subscribingto the channel, but can not be changed later,

SUMMARY OF THE INVENTION

Therefore, one object of the present invention is to dynamically changethe connection profile.

Another object of the present invention is to perform connection toanother server when one server is abnormally operated, or to implementload balancing.

In order to achieve these objects, the present invention provides aprotocol capable of dynamically changing configuration information,e.g., a connection profile.

In order to achieve these objects, the present invention also provides amethod for updating preset sessions based on a changed connectionprofile.

To achieve these and other advantages and in accordance with the purposeof the present invention, as embodied and broadly described herein,there is provided a method for updating a connection profile in acontent delivery service, comprising: receiving, from a server, aconnection profile update message including a connection profile;transmitting, to the server, a connection profile update confirmationmessage in response to the reception; transmitting, to the server, asession deactivation request message based on the connection profile;and transmitting, to another server, a session activation requestmessage base on the connection profile.

The connection profile may be a connection profile for a DCD-3interface.

The connection profile update message may be a ConnectionProfileUpdatemessage, and the connection profile update confirmation message may be aConnectionProfileConfirmation message. And, the session deactivationrequest message may be a ClientDeactivationRequest message.

The method for updating a connection profile in a content deliveryservice may further comprise receiving, from the server, a sessiondeactivation response message. The session deactivation response messagemay be a ClientDeactivationResponse message.

The method for updating a connection profile in a content deliveryservice may further comprise receiving, from said another server, asession activation response message.

The session activation request message may be a ClientActivationRequestmessage, and the session activation response message may be aClientActivationResponse message.

To achieve these and other advantages and in accordance with the purposeof the present invention, as embodied and broadly described herein,there is also provided a terminal for a content delivery service,comprising: a transceiver (transmitter/receiver); and a dynamic contentdelivery (DCD) client for updating preset connection profiles based on aconnection profile included in a connection profile update message whenreceiving the connection profile update message from the server throughthe transceiver, transmitting a connection profile update confirmationmessage to the server, transmitting a session deactivation requestmessage to the server through the transceiver based on the connectionprofile, and transmitting a session activation request message toanother server based on the connection profile.

In the present invention, a configuration file, e.g., configurationinformation about a DCD-3 interface is dynamically changed. This mayallow a DCD server which is in a mal-operation state to be replaced byanother DCD server, and enable load balancing.

The foregoing and other objects, features, aspects and advantages of thepresent invention will become more apparent from the following detaileddescription of the present invention when taken in conjunction with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this specification, illustrate embodiments of the invention andtogether with the description serve to explain the principles of theinvention.

In the drawings:

FIG. 1 is a block diagram showing a Dynamic Content Delivery (DCD)system in accordance with the conventional art;

FIG. 2 is a view showing an application profile and a channel profile;

FIG. 3 is an exemplary view showing a flowchart of a method for updatingconfiguration information according to the present invention;

FIG. 4 is an exemplary view showing configuration information, i.e., aconnection profile;

FIG. 5 is a flowchart showing a method for updating configurationinformation according to the present invention; and

FIG. 6 is a block diagram showing a DCD server and a DCD clientaccording to the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Description will now be given in detail of the present invention, withreference to the accompanying drawings.

The present invention is applied to a content delivery service, e.g., adynamic content delivery (DCD) service. However, the present inventionis not limited to this, but may be applied to all content deliveryservices to which the techniques of the present invention can beapplicable.

Unless differently defined, all the terms used herein with includingtechnical or scientific terms have the same meaning as terms generallyunderstood by those skilled in the art relating to the field of thepresent invention. Terms defined in a general dictionary should beunderstood so as to have the same meanings as contextual meanings of therelated art. Unless definitely defined in the present invention, theterms are not interpreted as ideal or excessively formal meanings.Furthermore, when the technical terms used in the present invention areunsuitable technical terms that do not precisely express the techniquesof the present invention, the unsuitable technical terms should bereplaced by suitable technical terms that can be understood by thoseskilled in the art. The general terms used in the present inventionshould be interpreted based on the previous or next contexts, but shouldnot be interpreted as an excessively narrowed meaning.

A singular expression includes a plural concept unless there is acontextually distinctive difference therebetween. In the presentinvention, a term of “include” or “have” should not be interpreted as ifit absolutely includes a plurality of components or steps of thespecification. Rather, the term of “include” or “have” may not includesome components or some steps, or may further include additionalcomponents.

Though terms of ‘first’, ‘second’, etc. are used to explain variouscomponents, the components are not limited to the terms. The terms areused only to distinguish one component from another component. Forexample, a first component may be referred to as a second component, orsimilarly, the second component may be referred to as the firstcomponent within the scope of the present invention.

When it is mentioned that one component is “connected” or “accessed” toanother component, it may be understood that the one component isdirectly connected or accessed to the another component or that stillother component is interposed between the two components. In themeantime, when it is mentioned that one component is “directlyconnected” or “directly accessed” to another component, it may beunderstood that no component is interposed therebetween.

Firstly, terms used in the present invention will be explained in brief.

Activation

In a content delivery system based on a point-to-point method such as aPUSH method or a PULL method, it is a first task to connect a DCDterminal and a DCD server with each other. This is referred to as‘Activation’.

Session

A result of the activation is referred to as ‘Session’. In order to setthe session, the DCD terminal has to deliver a user's information andauthentication-related information to the DCD server, and requests theactivation. Then, the DCD server delivers a session ID to the DCDterminal, thereby performing the activation.

The session may be considered as a substantial start of a DCD service.Through the session, changes of a user's channel subscription, channelguide information, a user's personalization, and customizationinformation are performed.

In a content delivery system based on a broadcast method, channel accessinformation (channel access point information) or Session DescriptionProtocol (SDP) is delivered from the DCD server to the DCD terminal.And, the DCD terminal accesses interest channels by using the channelaccess information or the SDP, thereby receiving content.

Hereinafter, preferred embodiments of the present invention will beexplained in more detail with reference to the attached drawings.Similar reference numerals are used to similar components in eachdrawing. When it is judged that detailed explanation about well-knowntechniques relating to the present invention causes the presentinvention to be unclear, the detailed explanation will be omitted.

Though the present invention may be variously modified and have severalembodiments, specific embodiments will be shown in drawings and beexplained in detail. However, the present invention may not be limitedthereto, but it is intended that the present invention cover allmodifications, equivalents, and alternatives within the scope of theclaims.

In FIGS. 3 to 6 of the present invention, detailed constructions of theDCD terminal 100, the content provider 200, and the DCD server 300 arenot disclosed. However, the detailed configurations of the DCD terminal100, the content provider 200, and the DCD server 300 in FIGS. 3 to 6should be explained based on those of components shown in FIGS. 1 and 2.

FIG. 3 is an exemplary view showing a flowchart of a method for updatingconfiguration information according to the present invention, and FIG. 4is an exemplary view showing configuration information, i.e., aconnection profile.

As shown in FIG. 3, a connection profile inside the DCD terminal 100 maybe updated by the DCD server 300 if necessary.

Here, the connection profile indicates a series of parameters aboutcommunication between the DCD terminal 100 and the DCD server 300through an interface. As aforementioned, the connection profile islocated at a lower hierarchy of the application profile. As shown inFIG. 4, the connection profile includes a parameter about an address ofa server, a parameter about a proxy, detailed configuration about dataconnection (e.g., data connection details), and broadcast-relatedconfiguration. The connection profile will be later explained withreference to FIG. 4.

In order to update the connection profile, the present inventionprovides a protocol composed of a connection profile update message, anda connection profile update confirmation message.

The present invention also provides a method capable of transmitting aconnection profile about a changed DCD server to a DCD terminal when oneDCD server which is in a service state is changed to another DCD serverdue to mal-operation or for load balancing, capable of terminating asession with the previous DCD server, and capable of setting a sessionwith the new DCD server.

More concretely, the DCD terminal 100 sets a session with a first DCDserver 301, and receives contents (S110). Here, the session may be setthrough the aforementioned DCD-1 interface, or the DCD-2 interface, orthe DCD-3 interface.

Then, the first DCD server 301 judges whether update, deletion, oraddition of configuration information about the interface, i.e., theconnection profile are required.

The update of the connection profile is required when an address of thefirst DCD server 301 is changed, or information of a proxy server ischanged, etc. When information is changed, the first DCD server 301generates a connection profile. Examples of the connection profile willbe explained with reference to FIG. 4.

The update of the connection profile is required when the first DCDserver 301 which is in a mal-operation state is to be replaced byanother DCD server for load balancing. In the case that a service isperformed by a second DCD server 302 not by the first DCD server 301,the first DCD server 301 receives a connection profile from the secondDCD server 302 (S120).

Then, the first DCD server 301 delivers a connection profile updatemessage to the DCD terminal 100 (S131). Here, the connection profileupdate message includes an updated connection profile. In the case thatdeletion of a connection profile inside the DCD terminal 100 isrequired, the first DCD server 301 includes a connection profile havingno element or parameter (or attribute) in the connection profile updatemessage. In the case that deletion of a connection profile inside theDCD terminal 100 is required, the first DCD server 301 may include onlya name of a connection profile in the connection profile update message.

The changed connection profile may be a connection profile generated bythe first DCD server 301, or may be a connection profile received fromthe second DCD server 302. And, the connection profile may be aconnection profile for the DCD-1 interface, or the DCD-2 interface, orthe DCD-3 interface. Examples of the connection profile will be laterexplained with reference to FIG. 4.

Once receiving the connection profile update message, the DCD client 101of the DCD terminal 100 delivers a connection profile updateconfirmation message to the first DCD server 302 (S132).

Then, the DCD client 101 of the DCD terminal 100 checks the receivedconnection profile inside the connection profile update message.

Here, when the connection profile inside the connection profile updatemessage includes no element, the DCD client 101 of the DCD terminal 100deletes the preset connection profile. In the case that only a name ofthe connection profile exists in the connection profile update message,the DCD client 101 of the DCD terminal 100 deletes the preset connectionprofile corresponding to the name.

However, when the connection profile inside the connection profileupdate message includes a changed element or parameter, the DCD client101 of the DCD terminal 100 updates the preset connection profile. Here,the process of checking the received connection profile and updating thepreset connection profile may be executed after S131 and before S132, orafter S141 or S142.

More concretely, when the received connection profile is a connectionprofile about the DCD-3 interface, the DCD client 101 of the DCDterminal 100 delivers the received connection profile to the DCD enabledclient application 102. And, the DCD enabled client application 102locates the received connection profile at a lower hierarchy of theapplication profile. When the received connection profile is aconnection profile about the DCD-1 interface or the DCD-2 interface, theDCD client 101 of the DCD terminal 100 locates the received connectionprofile at a lower hierarchy of the content metadata.

Since the first DCD server 301 is replaced by the second DCD server 302for service, when the DCD client 101 of the DCD terminal 100 is todeactivate the preset session with the first DCD server 301, it deliversa session deactivation request message, e.g., a client deactivationrequest message, to the first DCD server 301 (S141). When the DCD client101 of the DCD terminal 100 is to update the preset session with thefirst DCD server 301 based on the new Content Profile, it delivers thesession deactivation request message to the first DCD server 301. In thecase that content of other channels is to be continuously receivedthrough the preset session, the session need not be deactivated.Accordingly, the DCD client 101 of the DCD terminal 100 may not deliverthe session deactivation request message to the first DCD server 301.

The first DCD server 301 delivers a session deactivation responsemessage, e.g., a Client Deactivation Response message, to the DCDterminal 100 (S142).

When the first DCD server 301 is replaced by the second DCD server 302for service, the second DCD server 302 delivers a session triggeredmessage for setting a session, e.g., a Request For client Activationmessage, to the DCD terminal 100 (S151). Here, the session triggeredmessage may not be delivered.

When there is not the existing session between the DCD client 101 of theDCD terminal 100 and the second DCD server 302, the DCD client 101 ofthe DCD terminal 100 delivers a session activation request message forsetting a session, e.g., a client Activation Request message, to thesecond DCD server 302 (S152).

The second DCD server 302 delivers a session activation responsemessage, e.g., a client Activation Response message, to the DCD terminal100.

Then, a session between the DCD terminal 100 and the second DCD server302 is set, and the second DCD server 302 provides content to the DCDterminal 100 through the session.

FIG. 4 shows an example of a connection profile. The connection profileis a connection profile about the DCD-3 interface, and includes aDCD-3-connection-profile-name parameter and a DCD-3-connection-profileparameter. The DCD-3-connection-profile-name parameter indicates a nameof the connection profile.

The DCD-3-connection-profile parameter includes configurationinformation, more concretely, a DCD-server-address parameter, anetwork-selection parameter, a proxy parameter, a data-connection-detailparameter, and a broadcast-profile parameter.

The DCD-server-address parameter designates an address of the DCDserver, and the network-selection parameter designates which network isto be selected for access. And, the proxy parameter designates anaddress or a name of a proxy.

The data-connection-detail parameter includes an access point name (apn)parameter, an auth-method parameter, an auth-username parameter, and anauth-password parameter at a lower hierarchy thereof. The ‘apn’parameter designates an access point name used to set data connection,and the auth-method parameter designates an authentication method for aninterface. The auth-username parameter designates a user name forauthentication through a selected authentication method. And, theauth-password parameter designates a password for authentication.

The broadcast-profile parameter includes a cell-broadcast-message-idparameter, a bcast-access-info parameter, a service-fragment-referenceparameter, an access-fragment parameter, an sdp-description parameter ata lower hierarchy thereof. The cell-broadcast-message-id parameterindicates an identifier of a message (The Cell Broadcast Service messageIdentifier, logical Cell Broadcast Service channel, from which the DCDClient should expect DCD-3 interface data delivered via Cell BroadcastService). The bcast-access-info parameter designates connectioninformation to be delivered by using broadcast (OMA BCAST specificconnection details, e.g., multicast IP, port, and TSI, for file deliverysession over which the DCD Client should expect DCD-3 interface data tobe delivered via OMA BCAST). The service-fragment-reference parameterdesignates URI matching (URI matching the “id” attribute of the OMABSCAST service associated with the DCD-3 interface). And, theaccess-fragment parameter s includes access information (complete OMABCAST Service Guide “access” fragment as described in Section 5.1.2.47of (BCAST-TS_service_Guide) containing access information for the filedelivery session associated with the DCD-3 interface). And, thesdp-description parameter designates SDP that describes a connectionparameter.

As aforementioned, it is configured that the connection profile insidethe DCD terminal 100 can be updated by the DCD server 300 if necessary.This may allow one DCD server which is in a mal-operation state to bereplaced by another DCD server, and implement load balancing.

FIG. 5 is a flowchart showing a method for updating configurationinformation according to the present invention.

The present invention also provides a method capable of delivering aconnection profile about a changed DCD server to a DCD terminal when oneDCD server which is in a service state is changed to another DCD serverdue to mal-operation or for load balancing, capable of terminating asession with the previous DCD server, and capable of setting a sessionwith the new DCD server. The method for updating configurationinformation according to the present invention will be explained in moredetail.

Firstly, the first DCD server 301 which is performing a service providesa changed connection profile to the DCD terminal 100 (S210).

Then, the DCD terminal 100 stores the connection profile (S220). Moreconcretely, when the connection profile is a connection profile aboutthe DCD-3 interface, the DCD terminal 100 updates the applicationprofile by using the connection profile (S220). Here, the connectionprofile includes a DCD-3-connection-profile-name parameter as shown inFIG. 4. Accordingly, the DCD terminal 100 searches a parameter inside anapplication profile consistent with a designated name in the parameter,and updates a corresponding application profile.

Then, the DCD terminal 100 judges whether there exists a channelprovided through a session with the previous DCD server, i.e., the firstDCD server lo 301 (S230). If there is no channel, the DCD terminal 100deactivates the session (S240). However, if one or more channels exist,the DCD terminal 100 executes S250.

The DCD terminal 100 checks whether a session with a new DCD server,i.e., the second DCD server 302 is set, and whether there is a channelprovided through the session (S250).

If there exists no session and no channel, the DCD terminal 100establishes (or activates) a session with the second DCD server 302(S260). However, if there exists a session and a channel, the DCDterminal 100 terminates the current step.

As aforementioned, the connection profile is flexibly changed in thepresent invention. Accordingly, when one DCD server is mal-operated, itcan be replaced by another DCD server and load balancing is implemented.

The method of the present invention may be implemented by software,hardware, or combinations thereof. For instance, the method of thepresent invention may be implemented as codes or commands inside asoftware program that can be executed by a processor (e.g., amicroprocessor inside a mobile terminal). And, the codes or commands maybe stored in a storage medium (e.g., an inner memory of a mobileterminal, a flash memory, a hard disc, etc.). Hereinafter, withreference to FIG. 6, will be explained a case that the method of thepresent invention is implemented by hardware.

FIG. 6 is a block diagram showing configurations of a DCD server and aDCD client according to the present invention.

As aforementioned, the DCD server 300 may update, delete, or add theconnection profile inside the DCD terminal 100. The DCD server 300includes a storage means 310, a controller 320, and a transceiver 330.

The storage means 310 stores the connection profile, and the controller32 updates the connection profile inside the storage means 310 ifnecessary.

The transceiver 330 delivers a connection profile Update message to theDCD terminal 100 so as to deliver the changed connection profile to theDCD terminal 100, and receives a connection profile update confirmationmessage from the DCD terminal 100. And, the transceiver 330 receives aSession Deactivation message from the DCD terminal 100 so as todeactivate a session, and delivers a session deactivation responsemessage to the DCD terminal 100. The transceiver 330 receives a SessionActivation message from the DCD terminal 100 so as to activate asession, and delivers a session activation response message to the DCDterminal 100.

The DCD terminal 100 may update the connection profile according to arequest of the DCD server 300. The DCD terminal 100 includes a storagemeans 110, a controller 120, and a transceiver 130. Here, the DCD client101 and the DCD enabled client application 102 may be programs stored inthe storage means 110 and implemented by the controller 120.

The storage means 110 stores the connection profile. Once receiving anupdated connection profile, the controller 120 updates the connectionprofile inside the storage means 110.

As aforementioned, the transceiver 130 may receive the connectionprofile and the connection profile Update Request message. Thetransceiver 130 may transmit/receive the aforementioned another message,and its detailed explanation will be omitted.

The foregoing embodiments and advantages are merely exemplary and arenot to be construed as limiting the present disclosure. The presentteachings can be readily applied to other types of apparatuses. Thisdescription is intended to be illustrative, and not to limit the scopeof the claims. Many alternatives, modifications, and variations will beapparent to those skilled in the art. The features, structures, methods,and other characteristics of the exemplary embodiments described hereinmay be combined in various ways to obtain additional and/or alternativeexemplary embodiments.

As the present features may be embodied in several forms withoutdeparting from the characteristics thereof, it should also be understoodthat the above-described embodiments are not limited by any of thedetails of the foregoing description, unless otherwise specified, butrather should be construed broadly within its scope as defined in theappended claims, and therefore all changes and modifications that fallwithin the metes and bounds of the claims, or equivalents of such metesand bounds are therefore intended to be embraced by the appended claims.

1. A method for updating a connection profile in a content deliveryservice, the method comprising: establishing, by a mobile terminal, asession for content delivery service with a server; receiving, by themobile terminal from the server, a connection profile update messageduring the session; performing, by the mobile terminal, updateprocedures of a connection profile based on the connection profileupdate message; wherein the update procedures include: checking, by themobile terminal, whether at least one of a name of the connectionprofile and a connection profile element exists in the receivedconnection profile update message; when the name of the connectionprofile exists and the connection profile element is not present,deleting a pre-stored connection profile; and when the name of theconnection profile and the connection profile element exist in thereceived connection profile update message, updating the pre-storedconnection profile with the connection profile included in the receivedconnection profile update message; checking whether the session is keptgoing to be used by a client application in the mobile terminal;transmitting, to the server, a session deactivation request message whenthe session is not required; and transmitting, to another server, asession activation request message according to the updated connectionprofile.
 2. The method of claim 1, wherein the connection profile isconfigured for a DCD-3 interface.
 3. The method of claim 1, wherein theconnection profile update message is a ConnectionProfileUpdate message,wherein the session deactivation request message is aClientDeactivationRequest message, and wherein the session activationrequest message is a ClientActivationRequest message.
 4. The method ofclaim 1, further comprising receiving, from the server, a sessiondeactivation response message, wherein the session deactivation responsemessage is a ClientDeactivationResponse message.
 5. The method of claim1, further comprising receiving, from said another server, a sessionactivation response message, wherein the session activation responsemessage is a ClientActivationResponse message.
 6. The method of claim 5,wherein the received connection profile includes an address of saidanother server.
 7. The method of claim 1, wherein the connection profileincludes: a DCD-3-connection-profile-name parameter indicating a name ofthe connection profile; and a DCD-3-connection-profile parameterincluding setting information.
 8. The method of claim 1, wherein theconnection profile is located below an application profile.
 9. Themethod of claim 1, further comprising: transmitting, to the server, aconnection profile update confirmation message in response to thereception, wherein the connection profile update confirmation message isa ConnectionProfileConfirmation message.
 10. The method of claim 1,wherein the step of updating and the step of transmitting the connectionprofile update confirmation message can be performed in a reversedorder.
 11. The method of claim 1, wherein in the step of updating theconnection profile, an element or a parameter of a stored connectionprofile is changed according to the connection profile inside thereceived connection profile update message.
 12. The method of claim 1,wherein in the step of deleting the connection profile, if no element orno parameter is included in the connection profile inside the receivedconnection profile update message, or if only a name of the connectionprofile exists, the pre-stored connection profile is deleted.
 13. Aterminal for a content delivery service, the terminal comprising: atransceiver; and a DCD (Dynamic Content Delivery) Client, configured to:establish a session for content deliver service with a server; receive,from the server, a connection profile update message during the session;check whether a name of the connection profile exists in the receivedconnection profile update message; check whether a connection profileexists in the received connection profile update message; when the nameof the connection profile exists and the connection profile is notpresent, delete a pre-stored connection profile; when the name of theconnection profile and the connection profile exist in the receivedconnection profile message, update the pre-stored connection profilewith the connection profile included in the received connection profileupdate message; check whether the session is kept going to be used by aclient application in the mobile terminal; transmit a sessiondeactivation request message to the server through the transceiver whenthe session is not required; and transmit a session activation requestmessage to another server based on the updated connection profile. 14.The terminal of claim 13, wherein the connection profile update messageis a ConnectionProfileUpdate message, wherein the session deactivationrequest message is a ClientDeactivationRequest message, and wherein thesession activation request message is a ClientActivationRequest message.15. The terminal of claim 13, wherein the DCD Client is furtherconfigured to receive a session deactivation response message, from theserver through the transceiver, and a session activation responsemessage from said another server, wherein the session deactivationresponse message is a ClientDeactivationResponse message and the sessionactivation response message is a ClientActivationResponse message, andwherein the received connection profile comprises an address of saidanother server.
 16. The terminal of claim 13, wherein the DCD client isfurther configured to: transmit a connection profile update confirmationmessage to the server.
 17. The terminal of claim 16, wherein theconnection profile update confirmation message is aConnectionProfileConfirmation message.